-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore (anomaly detection): get anomalies proxy API #76707
Conversation
Codecov ReportAttention: Patch coverage is ✅ All tests successful. No failed tests found. Additional details and impacted files@@ Coverage Diff @@
## master #76707 +/- ##
==========================================
+ Coverage 77.17% 78.20% +1.03%
==========================================
Files 6896 6898 +2
Lines 306444 306573 +129
Branches 50230 50248 +18
==========================================
+ Hits 236510 239770 +3260
+ Misses 63468 60386 -3082
+ Partials 6466 6417 -49 |
ee1aa23
to
2c8b395
Compare
3d21b58
to
21adbe6
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
would it be possible to make this PR a bit smaller / split into multiple?
could start with just the endpoint definition w/ placeholders, then the seer logic as a follow-on.
additionally, if this is a new endpoint, i think it is fine to have it start as EXPERIMENTAL
Sure, I can break it up |
closed in favor of: |
Create a proxy for us to fetch anomalies from the frontend